One master has to generate the public and private keys. Then copy the private key to another master.

It works, thanks!

Issue should be fixed in Veyon 4.1.2 - please give it a try 😉

Hello! Welcome to Veyon! The public key should always be readable by everyone, so use a group such as "users " here.

looks like thumbnails resize nicely when I click on the Veyon notification icon twice. The first click minimizes the Veyon Master window; second click restores the Master window and the moniotored thumbnails get resized.
Oh, I also just discovered the slider and buttons along the bottom of the window - that's what I was looking for!

@alberto OK. Now I make it. The problem was "use VNC tool" in the Service Tab.

Question closed.

I'm trying to use vcpkg to build the required libraries and then use vs 2017(cmake) with vcpkg to generate the vs project.

The "Perform Access control at program start" option makes the Master application check whether the teacher is allowed to access computers at all. It's an additional check for convenience (which can lead to false positives, that's why you should try to disable it for the time being) but not strictly necessary as the actual access control is performed on client computers so that only authorized users will be granted access. If the option is disabled, anybody can start the Master but still will only be able to access clients he's really allowed to access.

@Tarloth you don't need LDAP to run Veyon. You can configure rooms and computers using the builtin network object directory. The only difference to iTALC is that room and computer management is done through the Veyon Configurator and not inside Veyon Master any longer.

Hi @mikep345678
the builtin passwort is generated randomly at runtime so it can't be used from the outside world. You can however install UltraVNC in parallel, set a password and configure Veyon to use this existing UltraVNC server.
Best regards
Tobias

Which directories are the plugin installed in? Please make sure they're located in /usr/lib64/veyon or pass a proper value to cmake via -DCMAKE_INSTALL_LIBDIR=/usr/....

just install it on master as master and on client without master checklist.

for password request in every enter the veyon master, you can enter configuration and set authentication on GENERAL with method: key file authentication (same method for master and client). if you have no idea, you can look at this video

Hi @mikep345678
thanks for your feedback and useful suggestion! I just added a new parameter "/NoStartMenuFolder" to the installer so starting from Veyon 4.1.2 (likely to be released this week) you can pass this parameter to the Veyon installer in your deployment software.
Best regards
Tobias

Lieber Tobias,

vielen Dank für deine Antwort. Ich antworte nochmal auf deutsch um diesen Thread abzuschließen aber werde zukünftig natürlich Englisch nutzen. Derzeit nutzen wir in der Tat noch ITalc aber würden lieber früher als später auf Veyon wechseln. Genau solche Möglichkeiten in Veyon beschleunigen das aber natürlich 😉
Ich melde mich.

Beste Grüße
Michel

@markuy48 This is a problem which unfortunately can occur in some situations due to restrictions in the input device interception driver used by Veyon - see https://github.com/oblitum/Interception/issues/25 for details. We currently do not have a solution for this, I'm sorry 😞

@GCNA_Mentor Yes you can use the graphical method for saving and loading the configuration. Alternatively you can automate this process in a batch file using the CLI tool veyon-ctl - see https://docs.veyon.io/projects/admin-manual/en/4.1/cli.html#configuration-management for details. This is the prefered method in order to perform this step on all client computers (which is necessary).

Once you're running Veyon upgrading is no problem. Either perform an in-place upgrade or in case something goes wrong, remove first, reboot and install the latest version. All settings and keys are preserved.